Gary A. Cooper
Senior Systems Architect, Horizons Consulting, Inc., United States
Within our organization, we had been utilizing Exchange Server 2007 UM in conjunction with Office
Communication Server 2007 R2. This solution worked well, but we
required the new features in Exchange Server 2010 UM—specifically
RMS-protected Voicemail and Voicemail Preview. When we originally
configured Exchange Server 2007 UM, we did not have enough Direct
Inward Dial (DID) numbers for each mailbox that was UM-enabled, so we
instead configured Exchange Server 2007 UM to use the auto attendant to
answer all inbound calls and then to prompt the caller to select the
appropriate person to contact. This worked well until we introduced
Exchange Server 2010 and DID numbers.
To implement Exchange Server
2010, we had to create a new dial plan for OCS to route properly to the
new UM server. This now forced each user to have two new EUM address
entries after we moved their mailboxes to Exchange Server 2010 and
migrated their UM to Exchange Server 2010 UM (by removing their old UM
settings and re-provisioning them).
EUM: [email protected];phone-context=<NewDialPlanName>
eum:<extension>;phone-context=<Exchange2010DialPlanName>
In testing, what we found
was that if a call came into OCS for a mailbox we had already moved to
Exchange 2010 UM, the main number would be answered by the auto
attendant in Exchange Server 2007 UM; then, when the older UM server
tried to route the caller to the Exchange 2010 UM server, it would
error and tell the caller "The call has failed, please press '0' (zero)
for the operator or dial someone by name or extension to reach them
directly." If the caller tried to dial by name or extension number to
mailboxes still on Exchange Server 2007 UM, it worked without issue.
Behind the scenes, Exchange UM couldn't find the migrated mailbox and
would route the call back to OCS 2007 R2, which would route it back to
Exchange UM, and so on, and eventually the call failed and the caller
was dropped.
In working with
Product Support Services, we determined that Exchange 2007 was still
looking for the proxy address for its dial plan in the following format:
eum:<extension>;phone-context=<Exchange2007DialPlanName>
We determined that when the
caller entered the extension (such as - 204), Exchange Server 2007 UM
would search for the user in the current dial plan (the dial plan
associated with the auto attendant that answered the call)—in this case
the Exchange 2007 Sip_Name dial plan. It did this search by
constructing the EUM address (204; phone-context=<Exchange 2007 Dial plan Name>.< Exchange 2007 Dial plan GUID>)
and then searching all Active Directory users to check whether any user
had this stamped in their proxy addresses. However, the migrated
mailbox that has been moved to Exchange 2010 UM-has been provisioned on
the new Exchange 2010 Sip_Name dial plan, so it no longer has the
Exchange 2007 proxy address, and so the user object is not located.
The solution we ended up
implementing was to add the legacy EUM proxy address back to the
mailbox object, thus enabling extension dialing from both Exchange 2007
and Exchange 2010 UM services.
|